Release 10.1A: OpenEdge Development:
Progress 4GL Reference

DEBUG-ALERT attribute

Indicates whether Progress provides access to 4GL stack trace information when an error occurs during a session (TRUE) or not (FALSE).

Data type: LOGICAL

Access: Readable/Writeable

Applies to: SESSION system handle

When an error occurs in an interactive session, for any 4GL client, Progress displays an alert box with a help button that displays a dialog box containing the 4GL stack trace information.

You can use the DEBUG-ALERT attribute on the SESSION system handle with the -clientlog startup parameter to access 4GL stack trace information during a session.

If you set DEBUG-ALERT to TRUE and use the -clientlog startup parameter, the 4GL stack trace is written to the log file you specify with -clientlog. Messages are written to the specified log file as they are encountered during a session. This applies to both interactive and batch sessions. For WebSpeed and AppServer applications, the output goes to their respective log files.

Note: If you do not use the -clientlog startup parameter to specify a log file name, messages are not written to a log file.

You can also set DEBUG-ALERT to TRUE using the -debugalert startup parameter. For more information about the -clientlog and the -debugalert startup parameters, see OpenEdge Deployment: Startup Command and Parameter Reference .